Walkthrough/guide building aplication server for multi tenant web app [on hold]

Posted by Khalid Adisendjaja on Server Fault See other posts from Server Fault or by Khalid Adisendjaja
Published on 2014-05-30T13:59:29Z Indexed on 2014/05/30 15:31 UTC
Read the original article Hit count: 313

The web app will detect a subdomain such as tenant1.app.com, tenant2.app.com, etc to identify tenant environment, each tenant environment will have a different database credential (port,db name,etc) but still connecting to the same database server. Each tenant should use app.com for their main domain, using their own domain is prohibitted.

Each tenant will have their own rest api endpoint such as tenant1.app.com/api/v1/xxxx, tenant2.app.com/api/v1/xxxx, tenant3.app.com/api/v1/xxxx

I've come to a simple solution by setting a wildcard subdomain (*.app.com) on webserver Apache/Nginx vhost configuration file. I have googled so many concept for building a multi-tenant app server but still don't understand how to really done it, what is the right way to do it and what is actually required to do this task.

So I've come to this questions,

  1. Do I need a proxy server, dns masking, etc..
  2. How to monitor each tenants activity
  3. What about server performance, load balancing, and scalability
  4. How to setup ssl certificate for each tenant
  5. what about application cache for each tenant
  6. Is it reliable to use the setup for production
  7. etc ...

I have a very litte experience on server infrastructure, so I'm looking for a DIY walkthrough, step by step guide, or sophisticate solution ready to implemented for production

© Server Fault or respective owner

Related posts about apache-2.2

Related posts about nginx